Resolving issue on specific domain

[Matus UHLAR - fantomas]

On 12.07.16 17:13, Daniel Dawalibi wrote:
>We are facing a weird issue while resolving a specific domain name from our
>authoritative DNS server running on BIND 9.10.4-P1
>
>Server has only one public IP address.
>
>If you try to resolve the domain using either dig or nslookup you will not
>get any result whereas if you specify @localhost you will get the answer
[...]

>#dig @localhost soa domainname
[...]

>#dig soa domainname
>;; SERVER: 194.126.10.18#53(194.126.10.18)

as you can see, in the latter example it's not the localhost (127.0.0.1) but
194.126.10.18 that gives you answer. That means, 194.126.10.18 does not know
the "domainname"

you must add localhost to resolv.conf as first nameserver to get answers
from it by default.

-- 
Matus UHLAR - fantomas, uhlar at fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Emacs is a complicated operating system without good text editor.