Bind: linux resolving, windows not
I have a weird problem. I set up a Bind DNS server on my Gentoo box this
week (Bind 9.3.2) to run my domain within my private network. Some entries will resolv to the local IP within the local LAN (given by my personal Bind server) while the big bad outside will get my external IP through the regular DNS servers. So far so good. - When I resolv a name (CNAME) locally, it works fine (duh) Code:
; <<>> DiG 9.3.2 <<>> knagers.somedomain.nl Code:
; <<>> DiG 9.3.2 <<>> knagers.somedomain.nl -Now the same box, just the windows (W2K) part of it (it's a dual boot). Code:
*** Can't find server name for address 192.168.1.69: Server failed WiFi router, and they are the same (same IP, same default gw, same DNS entries). So network settings can't be the problem... can they? Same problem (and error) on the WinXP box of my wife. It's a weird problem I haven't figured out yet, not even after some Googling and searching these forums. Hope someone can point me towards a solution (no, installing linux on the windows boxes is not a 'solution'... it's a workaround :D ). (domain names and ip's have been changed to protect the innocent) |
Try clearing the dns cache in Winders.
ipconfig /flushdns Also, you may have to do an ipconfig /release && ipconfig /renew to get WinXP to actually pick up the new settings. I had an issue when I first set up my network with all this type stuff, and I had to flush the dns and release/renew the IP manually. Seems XP likes to hold onto stuff like it shouldn't. |
Quote:
Also you can start bind with debug option (man named) From the windows you can ping the gentoo ? I guess you already tried that :) Can you telnet to the port 53 of the gentoo? from the windows : telnet 192.168.1.9 53. Maybe you miss an "acl" directive in bind option file. |
@ARC1450
Looks like Windows does try to query the server, but doesn't get a reply. I actually had the Win-boxes pointed towards the (now installed) primary DNS months ago, and my IPS's as secundary. But despite that, I did what you suggested and it didn't help. Quote:
Code:
C:\Documents and Settings\someuser.WINBOXES>nslookup -d knagers.somedomain.nl Quote:
Code:
named 7964 1 0 20:28 ? 00:00:00 /usr/sbin/named -u named -n 1 -t /chroot/dns |
Figured it out; there was an error in the IN SOA record of the reverse domain.
:rolleyes: "Check your logging whenever you have a problem Reef, that's what it is there for..." :rolleyes: Fixed the error, and now Windoze can resolv against the DNS too. |
Can you share more information about this?
I had the similar problem in my office :( |
All times are GMT -5. The time now is 04:22 PM. |