Transferring sites. DNS question

Started by xerbotdev, Sep 16, 2022, 02:51 AM

Previous topic - Next topic

xerbotdevTopic starter

Hello colleagues!
There is a virtual foreign server (VDS) that we rented for a long time and hosted our sites on it. Now we decided to move out of there and move the web sites to native web hosting. Who used to screw all that to server, screwed the DNS zone of the main domain there as well.

And that zone is hanging there in about that textual form:

$TTL 3600
@ IN SOA ns1.first-ns.de. postmaster.robot.first-ns.de. (
2019040100 ; serial
14400 ; refresh
3600 ; retry
604800 ; expire
3600 ) ; minimum

@ IN NS robotns3.second-ns.com.
@ IN NS robotns2.second-ns.de.
@ IN NS ns1.first-ns.de.

@ IN A 1x9.xx1.xx0.xx0 - external IP of the VDS server
* IN A 1x9.xx1.xx0.xx0 - external IP of the VDS
rols server IN A 1x9.xx1.xx0.xx0 - external IP of the VDS
crm server IN A 2xx.xx7.xx7.1xx - one of the white IP of our provider (our internal is hanging here.server)
.... IN A xхx.xхx.xхx.xхx
www IN A 1x9.xx1.xx0.xx0 - external IP of the VDS server

................
................

When will our web  site be transferred from that web hosting and the contents of the subdomain rols.xхxxхxxхxx.com (also one of our web resources), I will naturally need to change the IP addresses here, And the records opposite the rolls. and the records * and www, to the IP DNS server of the new web hosting, so that the requests go there?

But I don't understand what to do with the @ entries? I guess the @ (dog) entry says that the domain zone is <ours domain.com> lies on these servers?
@ IN NS robotns3.second-ns.com.
@ IN NS robotns2.second-ns.de.
@ IN NS ns1.first-ns.de.


and then what about the line - @ IN A 1x9.xx1.xx0.xx0 - external IP of the VDS server?

I have not posted all the contents of the zone, below there is also DMARC, DKIM records with them seem to be clear - we do not touch.
But there is for instance a line like this:
@ IN MX 0 <our domain>-com.mail.protection.outlook.com . (we have Exchange 365)

There is a string starting with the @ sign indicating the SPF record.
Do I understand correctly that since the DNS zone remains in the old place for now (only web sites are moving), then we change only the entries in the first block are * and www?
And in that line - @ IN A 1x9.xx1.xx0.xx0 - the external IP of the VDS server, or do you not need to touch that one?

I was just trying to find understandable information about a record like @, I found only a meager description that I didn't fully understand.

The rest of the lines starting with @ - do not touch?
Thank you.
  •  

Donna D. Phillips

To simplify it a lot for you, the @ symbol is placed at the beginning of the DNS record line if the name is missing.

>I think the @  entry says that the domain zone is <ours domain.com> is it on these servers?
>@ IN NS robotns3.second-ns.com .
>@ IN NS robotns2.second-ns.de.
>@ IN NS ns1.first-ns.de.

The final conclusion is correct, the specified servers are responsible for your domain zone, but it is not the @ symbol that indicates that, but the type of record with the letters NS - an abbreviation of the word NameServer

Do these three nameservers belong to a foreign web hosting?
If yes, then after the end of the contract, you will lose access to the DNS admin panel of this hosting and you will not be able to change anything later. Therefore, you need to change the nameservers for your domain zone. To do that, you need to find two nameservers that will hold your zone. This can be done by the provider and often for free, but it is better to order the DNS Hosting Primary and Secondary service from some registrar. It would be better to voice your domain and not hide it here, it would be clear where it is registered and who the registrar is. Surely your registrar provides both of these services and even for free if you bought a domain name through them.

The transfer of zones to new nameservers is simple. First, you add them in the zone admin panel to the list of existing nameservers, wait until the zones are transferred to new nameservers.
Then you delete unnecessary nameservers in the admin area of the domain zone. This should be done in the admin panel of the registrar of your zone.
  •