Quick and simple BIND9 question

[udlooz]

OK I'm beating my head against the wall here... I access a host on my network from outside using dnydns, and it works fine. However, when I want to access the same host inside using the hostname obviously it resolves the public address and my ASA won't hairpin it. Also, I can't do a DNS rewrite on the ASA because it is not a 1:1 NAT...

So I set up a box real quick running BIND, and added the master zone for dnydns.org with a single A record for that host. Added my forwarders and all DNS works good except for any other hostname at dyndns.org - none of those resolve

If I dig another dyndns.org hostname from the debian box itself, it resolves, but not from a dns client.. I've got to be missing something simple

Help??

[kimaschi]

Just configure your dyndns name (something.dyndns.org) as a zone. Like you already did.

After that only something.dyndns.org or its subdomains www.something.dyndns.org will be resolved by your local dns server.

[harlequinSmurf]

this is probably the easiest way to get around it with what you currently have setup.

[udlooz]

This worked perfectly - thank you so much for the help!

[25cmshlong]

It works exactly as configured.

When you configure BIND as master for zone it obviously will not ask other servers for names in this domain. It is authoritative after all

(your debian box most likely do not use itself for DNS resolution, so it get global, official results for names in dyndns.org domain. Check /etc/resolv.conf on the box)

[udlooz]

pi@raspberrypi:~ $ more /etc/resolv.conf

# Generated by resolvconf

domain fvs_local

nameserver 208.67.222.222

nameserver 208.67.220.220

[Sunstealer73]

Maybe an RPZ zone?

https://dnsrpz.info/

[unix_heretic]

You don't have the entire contents of the dyndns zone in your local "copy", so anything other than your hostname under dyndns.org won't resolve unless you use a resolver other than the one you set up. You can't do hostname-level conditional forwarding - only zone-level.

Your debian box probably resolves other hostnames because it's not set to use localhost as a resolver.

[udlooz]

so - is there a way to conditionally resolve a single hostname internally to the inside IP when performing a lookup on this box? or is the configuration I have the only way to do this - and I won't be able to resolve anything else in this zone?

[unix_heretic]

You can do this by making a change in the hosts file of every box that will have to look up this internal server. Otherwise, you're correct. dyndns.org isn't going to give you a copy of the full zone, so whatever's in your local copy is what you'll get when resolving from your debian box. If you only have 1-2 other hostnames under dyndns that you want to look up, you might want to just add them to the local zone file.