This is a new server where I am moving my old one.
Hosting company assigned my domain as blabla.bleble.com
I installed Web/virtualmin++ package successfully.
I’ve changed (put in first place) the hostname to simpleD.com simpleD.com is also a domain name I own and I’m not using.
In my registrar I’ve set NameServer Registration: ns1.simpleD.com ->IP#1 ns2.simpleD.com ->IP#2
and Domain Name Server Setup
DNS set to ns1.simpleD.com and ns1.simpleD.com
The other domain I own will be change in that way (only DNS)
Then I created a virtual host simpleD.com (from Virtualmin)
Do I need extra changes/adds?
I am asking it because in my old server, analog bind configuration contains records like
ns1 IN A IP#1
Without any changes in created virtual host, from intoDNS I get:
NS records got from your nameservers listed at the parent NS are: simpleD.com [’***.54’] [TTL=38400] (main IP)
while other domains in other servers display something like ns2.mydomain.com [‘.36’] [TTL=38400] ns1.mydomain.com ['.37’] [TTL=38400]
Missing nameservers reported by parent
FAIL: The following nameservers are listed at your nameservers as nameservers for your domain, but are not listed at the parent nameservers (see RFC2181 5.4.1). You need to make sure that these nameservers are working.If they are not working ok, you may have problems! simpleD.com
Missing nameservers reported by your nameservers ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are: ns2.simpleD.com ns1.simpleD.com
This is listed as an ERROR because there are some cases where nasty problems can occur (if the TTLs vary from the NS records at the root servers and the NS records point to your own domain, for example).
By default, what Virtualmin does is add an NS record to the DNS entries that is based on your system hostname.
It sounds like in your case, the system hostname isn’t actually the name of any nameservers defined at your registrar.
That’s okay, it just means you need to go into System Settings -> Server Templates -> BIND DNS Domain, and set “Master DNS server hostname” to be the name for your primary nameserver, and you may want to set a second one in “Additional manually configured nameservers”.
That will correct it for new domains.
For existing domains, you’ll need to go into Services -> DNS Domain -> Name Server, and set your nameserver records in there.
(just to maybe help others)
As you suggested some days ago in other post, I had set Webmin -> Networking -> hostname and dns client -> Hostname: myNewDomain.com (ns1.myNewDomain.com and ns2.myNewDomain.com are nameservers to set in registrars)
Question 1: From www.intodns.com I get this
Warn SOA Serial Your SOA serial number is: 1246110523. This can be ok if you know what you are doing.
Do you know what means if you know what you are doing ?
[cite]Warn SOA Serial Your SOA serial number is: 1246110523. This can be ok if you know what you are doing.
Do you know what means if you know what you are doing ?[/cite]
The short answer is that you can probably ignore that warning
It matters, sort of, what serial number is used. Many/most people use a serial number based on the current date.
It’s not necessary to do that, but I think their point is largely that serial numbers should not be chosen arbitrarily. But again, you can ignore that warning
[cite]dig @ns1.myNewServer.commyNewServer.com ns
dig: couldn’t get address for ‘ns1.myNewServer.com’: not found
How can I fix this?[/cite]
In addition to adding NS records for your nameservers, you may also need to add “A” (address) records.
Your NS record says what nameservers are authoritative. But you’ll also need an address record that says what the IP addresses are for ns1 and ns2.