My Debian server has two linked ns servers, ns1.w4u.com.ua and ns2.w4u.com.ua. However, after registering these servers for the domain soshichnezosh.com, the domain is not appearing. The registrar claims that there are no domain records on the specified NS servers. They've suggested that I contact the owner of the NS servers to request that they add records about the domain in the zone file.
To resolve this issue, I would need to configure bind properly for the domain registration.
QuoteGood afternoon.
There are no domain records on the specified NS servers:
; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> @NS1.W4U.COM.UA soshichnezosh.com any
; (1 server found)
;; global options: +cmd
;; ;; Get answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 9947
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;soshichnezosh.com. IN ANY
Please contact the owner of the NS servers so that they make
records about the domain in the zone file.
After configuring the NS settings for soshichnezosh.com, make sure to restart the name server with the command "rndc reload" - unless there's an error in the configuration. Additionally, it's important to describe the zone by following the example provided in the instruction that you linked in your question.
As an NS server administrator, you must create file zones for the domain soshichnezosh.com on the bind-deployed server that is directed by NS, specifying the SOA record and all the necessary records (A, MX, CNAME, NS). For example, create a zone file in /var/named/soshichnezosh.com.zone for bind9.
In the config file (/etc/named.conf), you need to specify that the file soshichnezosh.com.zone is the configuration file for the domain soshichnezosh.com and to identify the server type (master or slave). You'll then need to check if the domain is being polled for your NS using the command "dig soshichnezosh.com @ns1.w4u.com.ua". These are the minimum settings necessary, with the IP addresses presented as an example.
To describe the master zone of soshichnezosh.com, you'll need a separate file for each zone - the location of which isn't important, as long as it's convenient for backup purposes. For example, let's use the /etc/bind/masters directory to store the zone files, with the zone kept in a file with the same name (this can be arbitrary).
To incorporate this file into the bind program, you'll need to specify it in the configuration using the syntax "zone "soshichnezosh.com" {type master;file "/etc/bind/masters/soshichnezosh.com";}." If you have more than one zone, it's helpful to place all of these mentions of master zones in a separate file (which can contain many zones).
The meaning of the information given in the zone file can be found in many manuals or RFCs. One example is https://en.wikipedia.org/wiki/Zone_file.
The core problem here is that the domain registrar has informed you that there are no domain records on the specified name servers (NS), ns1.w4u.com.ua and ns2.w4u.com.ua. This suggests that the domain's DNS (Domain Name System) configuration is not properly set up, preventing the domain from being accessible.
Let's dive deeper into the steps you should take to address this:
1. Communicate with the NS server owner(s):
- Reach out to the owner(s) of the ns1.w4u.com.ua and ns2.w4u.com.ua servers and provide them with the details of your domain, soshichnezosh.com.
- Explain the issue you're facing, where the registrar is unable to find any domain records on these name servers.
- Request that they investigate the configuration of the zone file(s) on these servers and ensure that the necessary records for your domain are properly added.
- Coordinate with them to understand the timeline for making the required changes and when you can expect the updates to be completed.
2. Verify the zone file configuration:
- Once the NS server owner(s) have confirmed that they have updated the zone file(s) with the necessary records for your domain, you can use tools like dig or nslookup to verify the configuration.
- Perform a dig query for your domain (e.g., dig @ns1.w4u.com.ua soshichnezosh.com) to ensure that the response includes the expected records (A, MX, TXT, etc.).
- Analyze the output to confirm that the domain records are correctly configured and accessible through the specified name servers.
3. Update your domain's nameserver settings:
- After verifying the zone file configuration, you will need to update the nameserver settings for your domain soshichnezosh.com to point to the ns1.w4u.com.ua and ns2.w4u.com.ua servers.
- This step is crucial, as it ensures that your domain's DNS queries are directed to the appropriate servers, allowing users to access your website or other services.
- Consult your domain registrar's dоcumentation or support team to learn how to update the nameserver settings for your domain.
4. Monitor the domain's propagation:
- Domain changes, such as updating nameserver settings, can take some time to propagate across the internet's DNS infrastructure.
- Be patient and continue to monitor the domain's status, checking for any changes or updates using tools like dig or nslookup.
- Observe the response from the name servers and ensure that the domain records are being correctly resolved.
5. Communicate with your registrar:
- Keep your domain registrar informed about the steps you're taking to resolve the issue.
- Provide them with updates on the progress, such as the changes made to the zone file(s) on the NS servers and the updated nameserver settings for your domain.
- If necessary, work closely with the registrar's support team to ensure that the domain is properly configured and functioning as expected.