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
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41186
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;knagers.somedomain.nl. IN A
;; ANSWER SECTION:
knagers.somedomain.nl. 259200 IN CNAME sirius.somedomain.nl.
sirius.somedomain.nl. 259200 IN A 192.168.1.69
;; AUTHORITY SECTION:
somedomain.nl. 259200 IN NS ns.somedomain.nl.
;; Query time: 3 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Apr 3 20:20:20 2006
;; MSG SIZE rcvd: 94
- Now, for the linux install (also gentoo) on my laptop.
Code:
; <<>> DiG 9.3.2 <<>> knagers.somedomain.nl
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40375
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;knagers.somedomain.nl. IN A
;; ANSWER SECTION:
knagers.somedomain.nl. 259200 IN CNAME sirius.somedomain.nl.
sirius.somedomain.nl. 259200 IN A 192.168.1.69
;; AUTHORITY SECTION:
somedomain.nl. 259200 IN NS ns.somedomain.nl.
;; Query time: 2 msec
;; SERVER: 192.168.1.69#53(192.168.1.69)
;; WHEN: Mon Apr 3 20:07:31 2006
;; MSG SIZE rcvd: 94
Also working!
-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
Server: resolver.xs4all.nl
Address: 194.109.104.104
Non-authoritative answer:
Name: knagers.somedomain.nl
Address: 194.255.15.233
Weird part is that this particular box gets its network settings from my
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
).
(domain names and ip's have been changed to protect the innocent)