DNS Weirdness

Owen McShane owen at vianetworks.co.uk
Fri Oct 24 17:57:27 UTC 2003


Hi,

nslookup eoh.co.za will always fail, and dig eoh.co.za will always just
return the SOA, because you have no A records for eoh.co.za

digging for type any is a bit more fruitful:

[owen at bass owen]$ dig eoh.co.za any

; <<>> DiG 9.2.1 <<>> eoh.co.za any
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64083
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 4, ADDITIONAL: 2

;; QUESTION SECTION:
;eoh.co.za.                     IN      ANY

;; ANSWER SECTION:
eoh.co.za.              38322   IN      MX      10 eohmm.eoh.co.za.
eoh.co.za.              38322   IN      NS      eohns0.eoh.co.za.
eoh.co.za.              38322   IN      NS      eohns1.eoh.co.za.
eoh.co.za.              38322   IN      NS      asp1.eoh.co.za.
eoh.co.za.              38322   IN      NS      apollo.is.co.za.

;; AUTHORITY SECTION:
eoh.co.za.              38322   IN      NS      eohns0.eoh.co.za.
eoh.co.za.              38322   IN      NS      eohns1.eoh.co.za.
eoh.co.za.              38322   IN      NS      asp1.eoh.co.za.
eoh.co.za.              38322   IN      NS      apollo.is.co.za.

;; ADDITIONAL SECTION:
eohmm.eoh.co.za.        38322   IN      A       196.23.47.15
asp1.eoh.co.za.         38322   IN      A       198.54.229.4

;; Query time: 2 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Oct 24 18:56:24 2003
;; MSG SIZE  rcvd: 222

Owen


On Fri, 24 Oct 2003, Angela Williams wrote:

> Hi All,
> I've tried to search the archive fro the problem but have not had much jo=
> y.
> I admin both my master and one of my slave servers where we host about 10=
> =20
> domains for ourselves and customers.
> The current master lives on a linux box firewalled to the 'net running bi=
> nd=20
> 8.2.3.
> Everything works well except if I nslookup just the domain name.
> From a customer site (their own connection to the net) I get this result
> [root at gatekeeper /]# nslookup eoh.co.za
> Server:         168.210.2.2
> Address:        168.210.2.2#53
> 
> Non-authoritative answer:
> *** Can't find eoh.co.za: No answer
> [root at gatekeeper /]#
> dig gest this from the same site
> [root at gatekeeper /]# dig eoh.co.za
> 
> ; <<>> DiG 9.2.1 <<>> eoh.co.za
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24093
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
> 
> ;; QUESTION SECTION:
> ;eoh.co.za.                     IN      A
> 
> ;; AUTHORITY SECTION:
> eoh.co.za.              10261   IN      SOA     eohns0.eoh.co.za.=20
> awilliams.eoh.co.za. 2003102201 10815 3600 604800 38400
> 
> ;; Query time: 4794 msec
> ;; SERVER: 168.210.2.2#53(168.210.2.2)
> ;; WHEN: Fri Oct 24 09:00:56 2003
> ;; MSG SIZE  rcvd: 80
> 
> [root at gatekeeper /]#
> Dig gets the soa but zippo else.
> 
> Here's the named.conf and zone file for eoh.co.za
> named.conf
> options {
> =20       directory "/var/named";
> =20       pid-file "/var/run/named.pid";
> =20       notify yes;
> =20       };
> 
> 
> 
> zone "." {
> =20       type hint;
> =20       file "/var/named/db.cache";
> =20       };
> 
> zone "eoh.co.za" {
> =20       type master;
> =20       file "/var/named/master-zones/eoh.co.za.hosts";
> =20       notify yes;
> =20       };
> 
> And this is the top of the zone file itself.
> $ttl 38400
> eoh.co.za.      IN      SOA     eohns0.eoh.co.za. awilliams.eoh.co.za. (
> =20                       2003102301
> =20                       10815
> =20                       3600
> =20                       604800
> =20                       38400 )
> eoh.co.za.              IN      NS      eohns0.eoh.co.za.
> eoh.co.za.              IN      NS      eohns1.eoh.co.za.
> eoh.co.za.              IN      MX      10 eohmm.eoh.co.za.
> eohns0.eoh.co.za.       IN      A       196.30.202.139
> eohns1.eoh.co.za.       IN      A       196.23.47.200
> eohmm.eoh.co.za.        IN      A       196.23.47.15
> eohmes.eoh.co.za.       IN      A       196.23.47.16
> www.eoh.co.za.          IN      A       196.23.47.167
> 
> (I tried putting the A rr's for the 2 nameservers just below the mx recor=
> d=20
> hence the change in serial # - same result!)
> 
> I even tried installing baind  8.4.1 on my new firewall linux box but usi=
> ning=20
> the same named.conf and zone files as the existing dns server.
> 
> I've only look at this now as a sister company in Cape Town claims that t=
> hey=20
> cannot send mail to us as they cannot resolve the domain, mx record yes b=
> ut=20
> not domain!
> 
> Any ideas anyone? This was got me stumped!
> 
> Cheers
> Ang
> 
> --=20
> Angela Williams				Enterprise Outsourcing
> SCO Unix/Linux & Cisco spoken here!	Bedfordview
> awilliams at eoh.co.za			Gauteng South Africa
> 
> Smile!! Jesus Loves You!!
> 
> This message contains privileged and confidential information intended on=
> ly for the person
> or entity to which it is addressed.
> 
> Any review, retransmission, dissemination, copy or other use of, or takin=
> g of any action
> in reliance upon this information by persons or entities other than the i=
> ntended
> recipient, is prohibited.=20
> 
> If you received this message in error, please notify the sender immediate=
> ly by e-mail,
> facsimile or telephone and thereafter delete the material from any comput=
> er.
> 
> Any views expressed in this message are those of the individual sender, e=
> xcept where the
> sender specifically states them to be the view of the entity transmitting=
> =20the message.
> 
> 



More information about the bind-users mailing list