Primary name server not listed at parent как исправить

# dig +trace SERVER-BUSINESS.RU
...
SERVER-BUSINESS.ru.	345600	IN	NS	oxygen.ns.hetzner.com.
SERVER-BUSINESS.ru.	345600	IN	NS	hydrogen.ns.hetzner.com.
SERVER-BUSINESS.ru.	345600	IN	NS	helium.ns.hetzner.de.
;; Received 644 bytes from 194.190.124.17#53(d.dns.ripn.net) in 72 ms
...
SERVER-BUSINESS.RU.	3600	IN	A	135.181.20.85
SERVER-BUSINESS.RU.	3600	IN	NS	robotns3.second-ns.com.
SERVER-BUSINESS.RU.	3600	IN	NS	robotns2.second-ns.de.
SERVER-BUSINESS.RU.	3600	IN	NS	oxygen.ns.hetzner.com.
SERVER-BUSINESS.RU.	3600	IN	NS	ns2.SERVER-BUSINESS.RU.
SERVER-BUSINESS.RU.	3600	IN	NS	helium.ns.hetzner.de.
SERVER-BUSINESS.RU.	3600	IN	NS	hydrogen.ns.hetzner.com.
SERVER-BUSINESS.RU.	3600	IN	NS	ns1.first-ns.de.
SERVER-BUSINESS.RU.	3600	IN	NS	ns1.SERVER-BUSINESS.RU.
;; Received 316 bytes from 193.47.99.5#53(helium.ns.hetzner.de) in 77 ms

То есть, на родительском NS-сервере указаны только три NS-сервера, а на основном NS-сервере их указано восемь. А эти списки должны совпадать.

Похожие темы

• Форум
  Name server (2000)
• Форум
  FTP-server LIST (2004)
• Форум
  parent squid for isa server (2007)
• Форум
  WARNING **: AT-SPI: Could not obtain desktop path or name (2017)
• Форум
  Конфликт vpn server и vpn клиента на mikrotik (2016)

• Форум
  stay at home server (2008)
• Форум
  access control list server (2012)
• Новости
  «Securing your name servers» (1999)
• Форум
  python, NameError: global name NAME is not defined (2018)
• Форум
  does not name a type… (2013)

Which IP Addresses do your monitoring servers use?

In order to minimize false positives due to connection problems by our monitoring services we ask that you please whitelist these IP ranges on your firewall or network security systems:

• US-EAST-1A: 44.194.168.193/32
• US-EAST-1B: 52.55.244.91/32
• US-EAST-1C: 18.205.72.90/32
• US-EAST-1D: 18.209.86.113/32

---

Where can I find more information about an alert or error?

You can see details about different warnings and errors from our tools on the Problem Details page.

---

How do I delete a monitor from the dashboard?

To delete a monitor from the dashboard, follow these steps:

-Click on the card of the monitor you want to remove.

-Once the information populates on the right-hand side of the dashboard, do the following:

1. Click on Edit

2. Click on Delete Monitor

3. Click on Confirm Delete

---

How do I add tools to My Favorites?

To add lookup tools to My Favorites, please follow these steps:

1. Select the dropdown arrow from the SuperTool lookup.

2. From here, you can select Email, Network, Website, DNS, or All Tools.

3. In each tab, there is an icon that shows “Drag to Favorites+”.

4. Select the tool you want to add and drag it into the “Drag to Favorites” box.

5. Once you have added your first tool to “My Favorites”, a new “My Favorites” tab will appear on the SuperTool menu.

---

Where can I find more information about an alert or error?

You can see details about different warnings and errors from our tools on the DNS Problem Details page.

---

I have an error for Primary Name Server Not Listed at Parent. What does that mean?

We recommend that you contact your Domain’s Registrar to update the name servers on record to include the server that is not listed at the Root Servers.

————————————

About DNS Primary Server Listed at Parent

Your Primary Name Server was not on the list of name servers given to us by the root.

If your name server is not listed at the root, it could cause impaired/incorrect lookups for your domain.

Additional Information

The Primary Name Server is the name server declared in your SOA file and is usually the name server that reads your records from zone files and is responsible for distributing that data to your secondary name servers. This problem is present when this primary name server is not included in the parent referrals and is almost always accompanied by a Local Parent Mismatch problem.

RFC 1035:

Here a primary name server acquires information about one or more zones by reading master files from its local file system, and answers queries about those zones that arrive from foreign resolvers. [RFC 1035]

DNS Propagation Check

If your Primary Name Server is not listed at your Parent or is not responding, then our DNS Propagation test tool will not operate properly. You will most likely also be experiencing other real-world problems with DNS queries for your domain. Users with Basic or Pro accounts can contact our Support Team for assistance with understanding any DNS warnings or errors with specific information about your domain. If you are still a free user, upgrading your account will give you access to support, as well as many other benefits.

Have a great day!

---

What does «DNS Change Alerts Due to TTL Changes» mean?

If you receive a DNS change alert from MxToolbox because of TTL changes, no need to panic. These incidents are typically caused by issues at your DNS hosting provider.

DNS TTL (time to live) is a setting that tells your DNS resolver how long to cache a query before requesting a new query. The gathered information is then stored in the cache of the recursive or local resolver for the TTL before it collects new, updated details.

For example, if your DNS TTL is set to 3,600 seconds (60 minutes), the DNS resolver will have to regather the details of a website (mxtoolbox.com) every hour. If 100 users visit our site during that time, they will all see the same visual until the resolvers update their TTL.

The TTL acts as a stopwatch for how long to keep a DNS record because it represents the time each step takes for DNS to cache a record. Recorded in seconds, using the best TTL time for your situation is key to your site’s overall responsiveness.

MxToolbox often sees warning signs of issues and outages at DNS providers. Nearly every case is a problem with the specific DNS provider. For example, this outage occurred on May 5th, 2021, and affected customers’ domain DNS servers: DNS outage.

To check the propagation of DNS records across your servers and see the selected TTLs, use our DNS Propagation Tool.

---

Why am I receiving down alerts for Mailflow?

If you are receiving alerts for your Mailflow monitor and you are still able to send and receive email, chances are we did not receive a test message back to our system.

Click on the monitor and let it populate in the right window of the page. Under the graph you will see Outages | History | Pings | Edit > Click on Pings.

There are two (2) different results under the Pings table.

1. A message with a Green Check is a successful message returned to us. You can click on the details link and it will provide you the full headers and more information about the test message.
2. A message with a Red X on it is a failed message. If you click on Error, this will show you the test message’s subject.

If the message is failing:

• Use the message subject to check that it is not being filtering by an inbound appliance or spam software.
• Use the message subject to check your outbound SMTP logs to see if the message is leaving your gateway.

---

What does «Warning — Masked External Banner (Reverse DNS Failing)» mean?

When using the SMTP Diag tool, you see the banner you are displaying publicly is masked by asterisks:

Trying 1.2.3.4…
Connected to smtp.example.com.
220 *********************************************

The reverse check takes the banner and the PTR record for the IP address and sees if the domain is listed. Since all we get publicly is the asterisks, the comparison fails and you get the warning.

Many administrators choose to mask their banner in hopes that by not giving an attacker a domain name, they might avoid something like a directory harvest attack. If you are using a single IP address for inbound and outbound, then you need your domain in your PTR records for your outbound, so it should also be in your banner. However, this is personal preference, and nobody should deny sending or receiving mail from your server just because your banner does not contain your domain.

---

What does «Reverse DNS does not match your SMTP Banner» mean?

The reverse IP address name (PTR) is not contained in the server HELO or EHLO banner. In the example below, the string «someotherdomain.com» is not found anywhere in the server banner, which is reporting «example.com». This is only a warning, and in some cases you might not have control over it.

Example of incorrectly matching pair:

220 mx.example.com StrongMail SMTP Service at Wed, 09 Sep 2009 17:00:01 -0700

Not an Open Relay.
0 seconds – Good on Connection time
0.156 seconds – Good on Transaction time
OK – 1.2.3.4 resolves to mail.someotherdomain.com

Best practice would have 1.2.3.4 resolve to mx.example.com

Some mail servers look for this and use it to mark messages you send as questionable. Most mail systems will not reject your messages outright, but this might affect your spam score, increasing the likelihood that your messages will be marked as spam. We recommend that you contact your ISP and ask them to set up a reverse record (PTR) that matches the hostname of your mail server.

---

What does «Reverse DNS FAILED! This is a problem» mean?

When a sending server makes a connection to the recipient server, the recipient server notes the sending IP address and performs a reverse lookup. This is done by sending a DNS query, which returns a Fully Qualified Domain Name (FQDN) registered for that IP address. If the sending SMTP address matches the domain, then it is much more likely that the message is legitimate and, therefore, will be passed on to the recipient. If the IP address does not match, it is much more likely that the sending address was spoofed and, therefore, much more likely that it is unwanted and could be considered spam.

A Fully Qualified Domain Name (FQDN) is associated to an IP with a valid PTR record. You want the domain name portion of the FQDN to match the domain of your email address (e.g., If your sending addresses follow the convention of name@mydomain.com, your PTR record should contain something like mailserver.mydomain.com). Only the organization that controls and owns the IP can set a PTR record. PTR record queries are sent to the owner of the IP address, which is the ISP, unlike other DNS queries which are sent to the DNS server of whoever owns the domain. For this reason, setting a PTR record on your own DNS servers is essentially useless since no one is asking your servers.

To make any changes to your rDNS, you will need to contact your ISP. Or, if you host your own DNS (rare), you will adjust it yourself. You will not be able to do this in your DNS control panel unless your ISP also hosts your DNS and gives you the functionality to add your own rDNS records.

---

Gmail Help

Sign in

Google Help

• Help Center
• Community
• Gmail
• Privacy Policy
• Terms of Service
• Submit feedback

Send feedback on…

This help content & information

General Help Center experience

• Help Center
• Community
• New to integrated Gmail

Gmail

Stay on top of the new way to organize a space. Learn more about in-line threading.