DNS has broken using bind9 - Please help fix

[ashley.bye]

All sorted for home.mydomain.uk. Reverse lookups were working fine but forward lookups still gave an error. Running named-checkzone home.mydomain.uk /etc/bins/zones/db.home.mydomain.uk gave an "ignoring out-of-zone data (internal)" error. Changing internal., external., etc back to internal.home.mydomain.uk etc fixed this.

[SeijiSensei]

Just a hint for building domain.uk along with home.domain.uk. You'll need to create a separate zone file for domain.uk and include a record like this:

home     IN     NS     192.168.1.1

which tells it to look to the 192.168.1.1 server for the home subdomain.

[darkod]

Is that why a record of type:

external   IN   A   192.168.1.2

didn't work? The OP says he has to put the FQDN to resolve correctly. Usually you put only the host(name) and the domain part is taken from the zone itself.

But in this case it was a home subdomain so that might make a difference.

[SeijiSensei]

In the zone file as posted, "external" is the short name for "external.home.domain.uk". How that is handled by the resolver on a client machine depends on how the "domain" and "search" fields are configured in /etc/resolv.conf. If that has "search domain.uk" then "ping external" translates to "ping external.domain.uk" which is not defined. If resolv.conf has "search home.domain.uk" then "ping external" should work. Another option is to include search entries for both domain.uk and home.domain.uk in resolv.conf, or use "domain domain.uk" along with "search home.domain.uk".