I have an odd issue that I cannot seem to figure out.  My unraid server cannot resolve itself for a dns lookup. I have a static IP configuration and the default gateway and dns servers are correct. Even with DHCP I have the same result. It's causing some trouble for some of my docker containers. It's been working fine but started acting like this when I rebooted the server 2 days ago.

 

Not even sure where to look at this point. Any ideas would be appreciated.  Attached is my network.cfg.

network.cfg

I have an odd issue that I cannot seem to figure out.  My unraid server cannot resolve itself for a dns lookup. I have a static IP configuration and the default gateway and dns servers are correct. Even with DHCP I have the same result. It's causing some trouble for some of my docker containers. It's been working fine but started acting like this when I rebooted the server 2 days ago.

 

Not even sure where to look at this point. Any ideas would be appreciated.  Attached is my network.cfg.

Have you tried instead of setting the DNS address to the router to rather set it to the same IP's of the DNS servers that the router itself is using? 

That won't help me because the router resolves the internal DNS address on my network. Understand.... I can resolve any other address just fine. I just cannot resolve the unraid server itself.  ex: unraid.mynetwork.com. I can resolve all of my other systems internally and general dns queries just fine. It's the weirdest behavior and I haven't had any issues up until my reboot two days ago.... before that reboots were fine.

Can other computers on your network resolve unraid.mynetwork.com successfully?

Yes they can....

 

I did some further testing..... I realized that I was incorrect in stating that I could resolve anything except itself.... I cannot resolve anything on the mynetwork.com domain, including itself. I get "Unknown host" .... although all other systems using the same dns server can resolve mynetwork.com. (just for clarification mynetwork.com is a fake domain.... I just prefer to not post actual information." Even VM's running on unraid can resolve just fine. Unraid and the docker containers are the ones that don't seem to be able to resolve.

 

another side question: nslookup doesn't seem to be part of the unraid OS. is there a command that will do the same (more or less)? I need to make sure unraid is actually using the dns in the config. Just to be sure.

 

 

nslookup

isn't as popular as it used to be. Normally I'd suggest either

dig

or

host

instead but they aren't included either. Nor are they in the Nerd Pack. I'll post a request. EDIT: I just looked more closely. They are included in the

bind

package in Nerd Pack.

 

What does your /etc/resolv.conf file look like? Mine looks like this:

 

root@Lapulapu:~# cat /etc/resolv.conf

# Generated by dhcpcd from br0.dhcp

# /etc/resolv.conf.head can replace this line

domain grafton.lan

nameserver 172.26.147.254

nameserver 8.8.8.8

# /etc/resolv.conf.tail can replace this line

root@Lapulapu:~#

 

 

I have nerd pack installed..... Bind is installed as well.... however, I cannot seem to find dig anywhere. EDIT: Well its seems that bind is not installing.... It says it's installing but it's status shows NO under installed.... odd because its the one thing I need and it's the only one in the NerdPack that won't install.... Ugh I cannot seem to catch a break here.

 

Here is my resolv.conf.

 

# Generated by dhcpcd from br0.dhcp

# /etc/resolv.conf.head can replace this line

domain mynetwork.local

nameserver 10.168.1.254

# /etc/resolv.conf.tail can replace this line

 

I know the DNS is working because I can resolve external addresses google.com, msn.com etc. Other systems on my network use the same DNS with no secondary so I know the DNS server is working.

Yes, I noticed that about Nerd Pack too. It had downloaded the bind package but hasn't installed it. Does it need a reboot?

 

I'm a bit confused because in your earlier post you referred to your domain as mynetwork.com but in your last post you referred to it as mynetwork.local. I realise you're reluctant to disclose your real domain name but your redactions are making it difficult to work out what's really going on. The reason I mention this is because there's something special about the .local pseudo-TLD as it's used by mDNS and zero configuration utilities. See here: https://en.wikipedia.org/wiki/.local Are you really trying to use it on your name server? I believe it's best not to so I always use the .lan pseudo-TLD for purely local domains as it's guaranteed not to confuse things.

Well.... I found the issue.... apparently my unraid server has been in some sort of a frelationship with my router.... they must have had a fight because my router is being a bitch and totally ignores queries from the unraid server......

 

I reset my router to factory and manually rebuilt the config (painful) but now my unraid box knows itself again. No idea what happened.... perhaps I was hit by that DDNS attack because now that I think about it, that was when my trouble started.