Centos 8 - Named problem

[arky_]

I have a problem with named. Following the instructions, I added a second IP address (administrator) and assigned this address to Admin. Later (reseler) - Name Servers and I created for my two IP named servers IP 1 - ns1 ..., IP 2 - ns2 ...
At the domain extension, I redirected to my new DNS servers (ns1 io ns2)
Seems trivial, but the command

"netstat -lnp | grep named"

it will only show my first IP (ns1)!
I manually added two lines to named.conf:

listen-on port 53 {xxx.xxx.xxx.10; };
listen-on port 53 {xxx.xxx.xxx.11; };

but also to no effect.
Where did I go wrong?

 

[Richard G]

Firstly you should not add lines to named.conf. Remove them again.
Named.conf should look like this:

options {
        //listen-on port 53 { 127.0.0.1; };
        //listen-on-v6 port 53 { ::1; };

etc. since it listens by default on port 53.

Normally I use the old method so add the ip ad admdin level. Add ip, click both and "assign to admin". You already did this.
Then I go to reseller level (still as admin) and click nameservers.

Select both ip's and then use "create ns1 and ns2 domain.com" where domain.com is your ns domain.
Also check both nameservers below there are mentioned correctly.

Then go to your domain.com for example if you have ns1.arky.com then go to arky.com on user level -> DNS management and verify that both the A records exist like
ns1.arky.com. A 192.168.0.1 (example ip's)
and
ns2.arky.com. A 192.168.0.2
(mind trailing dot) with the according correct ip
and also both NS records like:
ns1.arky.com. NS ns1.arky.com.
ns2.arky.com. NS ns2.arky.com.
mind the trailing dot again.

Seems it can also ben done via admin level DNS manager, but I always do it like this and never failed to setup good working nameservers.

 

[arky_]

that's what i did as you do. Here are my screey.

DNS Management

IP Manager

Name Servers

and here is my named.conf


Whereas "netstat -lnp | grep named" still only shows one IP


However, I do not know why intodns.com shows ns2 -> 176.115.253.102

 

[Richard G]

Oke as said. Remove those 2 entry's in /etc/named.conf they should not be there!!

The problem is in your A record. For ns2 you have ip 176.115.253.102 instead of 176.115.253.11 so you made a typo there.

 

[arky_]

which remove these (I have commented)

//listen-on port 53 { 127.0.0.1; };
//listen-on-v6 port 53 { ::1; };

or those

listen-on port 53 { 176.115.253.10; };
listen-on port 53 { 176.115.253.11; };

without this second example there was the same effect.

The domain at my domain registrar is explicitly configured to my two IP addresses

 

[Richard G]

or those

Both, see my 2nd reply, normally only the first 2 are present, so localhost, commented out by the lines, that's the way it should be.

The domain at my domain registrar is explicitly configured to my two IP addresses

Yes, but not in directadmin. You have used .102 on the second NS in Directadmin instead of .11 so that is why you have that issue.

Wait, I make a screenshot for you, look at the arrow.

 

[Richard G]

Additionally, you have a DNS propagation issue anyway.
web-hosting24.pl can not be found by my ISP at home and not by dnsstuff at this moment.

 

[arky_]

Sorry, the one below is up to date. The previous one was from 26-10-2020. Could DNS not be updated yet?

 

[factor]

Sorry, the one below is up to date. The previous one was from 26-10-2020. Could DNS not be updated yet?
View attachment 3830

up to 72 hours

normally for me it's about 2-8hrs

 

[Richard G]

In this case I think something went wrong with the registrar, your nameservers are set up according to your screenshot, but it looks like they are not pushed by the registrar. Because otherwise at least the nameservers should already be pingable or should be able to be found via nslookup, which is not the case.

Have a look at this:

DNS Checker - DNS Check Propagation Tool

Check DNS Propagation worldwide. DNS Checker provides name server propagation check instantly. Changed nameservers so do a DNS lookup and check if DNS and nameservers have propagated.

dnschecker.org

Not even present in Poland. That is very odd. Within your own country it shouldn't take more than 24 hours normally.