name server configuration

catiewong · 11-20-2018, 08:51 PM

The below is my named server configuration .

#vi /etc/named.conf

Code:

acl "trusted" {
        192.168.1.100;    # ns1 - can be set to localhost
"
};
"

 allow-query     { any; };
"

include "/etc/named/named.conf.local";

#vi /etc/named/named.conf.local

Code:

zone "mydomain.com" {
    type master;
    file "/etc/named/zones/db.mydomain.com"; # zone file path

 };

# vi /etc/named/zones/db.mydomain.com

Code:

@       IN      SOA     ns1.mydomain.com. admin.mydomain.com. (
                              3         ; Serial
             604800     ; Refresh
              86400     ; Retry
            2419200     ; Expire
             604800 )   ; Negative Cache TTL

; name servers - NS records
    IN      NS      ns1.mydomain.com.

; name servers - A records
ns1.mydomain.com.          IN      A       192.168.1.100
test.mydomain.com    IN A    192.168.1.100

I use another server which in the same subnet , I added the below line in /etc/resolv.conf , it do not work.

Code:

nameserver 192.168.1.100

it works if I added this lines .

Code:

server mydomain.com
nameserver 192.168.1.100

I just would like to ask , why I need to add "server mydomain.com" to resolv.conf , if I setup the name server IP address ( 192.168.1.100 ) in our client ( the client server may be is windows server ) , how to set "server mydomain.com" in client side ? or is it the reason that it needs the line "server mydomain.com" is because my name server configuration has problem ?

berndbausch · 11-20-2018, 09:54 PM

You say “it doesn’t work”. Precisely what doesn’t work?

What do you do, what do you expect to happen, what happens in reality?

I have to guess. The command ping test tells you that it doesn’t know test. If so, it’s because your DNS server has no record for test. It only has a record for test.mydomain.com. For this reason, you have to tell your resolver to automatically add mydomain.com. But I am not sure what doesn’t work and have to guess.

Regarding Windows, I googled windows dns client configuration and found this very informative site. mydomain.com is the primary DNS suffix.

TenTenths · 11-21-2018, 07:06 AM

You also have a mistake in the last line of your zone file:

This:

Code:

test.mydomain.com    IN A    192.168.1.100

Should be this:

Code:

test.mydomain.com.    IN A    192.168.1.100

You can also leave the .mydomain.com. part out of any records as this is implied.

So you could just use:

Code:

test    IN A    192.168.1.100