WHM - Mismatched NS records with a GoDaddy domain - dns

I have a WHM at Tilaa and a couple of domains with Godaddy.
I wanted to use pieronanni.it and pieronanni.com so I created a cPanel for pieronanni.it and added an alias for pieronanni.com, and in Godaddy I edited the server domains for pieronanni.com with ns1.pieronanni.com and ns2.pieronanni.com
The problem is that pieronanni.com does not work and this tools gives me this errors, is It a Godaddy configuration or WHM configuration?
I've tried editing the NS for pieronanni.com in WHM with ns1.pieronanni.com. and ns2.pieronanni.com. but nothing happened

Upon checking I could see that the nameserver for the domain pieronanni.it is using godaddy nameserver. And also I could see that some propagation delay for that domain.
ns81.domaincontrol.com
ns82.domaincontrol.com
And upon checking we could see that nameserver for that domain pieronanni.it is not resolving correctly.
ping ns2.pieronanni.com
ping: unknown host ns2.pieronanni.com
So first you need to create a custom nameserver.
Step 1: Point the server IP to your custom nameserve in registrar end.
Step 2: Add the custom nameserver in your WHM edit DNS zone and point NS1 and NS2 to server IP.
Please check.

Related

DNS CNAME pushed from somewhere

i have a mail server behind CloudFlare and when i check some logs and other DNS tools i seen a MX dc-abefc4aaxxxxx that isn't registered in my dns configuration in cloudflare. I tryed checking SOA and always shows cloudflare's name servers.
How can i really see where is this register being pushed?
Finally i solved this issue. Ocurrs when A record to Mail server is proxied and MX not. To solve this unproxy A record.
Here is the solution
https://support.cloudflare.com/hc/en-us/articles/360020296512-DNS-Troubleshooting-FAQ

vps nameserver setup not working

I am a noob in the VPS-DNS world.
I purchased a VPS (with one ip) and logged into WHM to setup for production. I configured nameservers to "ns1.a-domain-i-have.com" and "ns2.a-domain-i-have.com".
Then logged into that domain account at my register where I
- set default nameservers from the registrar
- in DNS manager I set ns1, A , my server IP and ns2, A, the same server IP
After creating a host account in WHM using "another-domain-I-have.com", I registered "ns1.a-domain-i-have.com" and "ns2.a-domain-i-have.com" in the custom nameservers.
But my new website refuse to work/ nothing works, I did all these based on the understanding of tutorials I googled.
I have tried
- reinstalled the VPS
- used the default nameserver that came with the VPS host. Although, this nameserver ip is unknown.
- update cPanel
I need some help!
I already got it. It works now. The steps I mentioned aboved did it. Maybe am supposed to take this down but I'll leave it for newbies like me.

DNS using BIND with Subdomains - Multiple Servers and Hosting Accounts

Hopefully someone can help clarify this.
I have a domain ie example.com registered with Go Daddy. I host the website with TSOHost so in my domain configuration, I have set the following NS records.
Nameserver 1: ns1.tsohost.co.uk
Nameserver 2: ns2.tsohost.co.uk
I am now able to serve the website both www and non www from this hosting package. I simply have an A record for example.com and a CNAME for www.example.com to point to example.com (this is being configured in the cpanel Advanced DNS Zone Editor). So now we have the website showing as expected and required.
I would also like to setup a kind of DDNS service using a different server entirely, (this will hold DNS records that I will create on the fly using a Radius database).
So I want to use the subdomain ddns.example.com for this DDNS service, ie bob.ddns.example.com for Bob (so that when I ping bob.ddn.example.com, I can alter the IP to 8.8.8. say). In Cpanel I have an A record for ddns.example.com and an A record for *.ddns.example.com to point to my server that will manage this, for example 85.214.214.214.
I have installed Bind on the server (currently using a digital ocean server for this, to which I have added ddns.exmaple.com as an A record to the droplet and *.ddns.example.com also), I have created a zone for ddns.example.com, within this I have set the ns record as the digital ocean details.
I have then added the following to my file /var/named/ddns.example.com.hosts
$ttl 38400
ddns.example.com. IN SOA ns1.digitalocean.com. jon#example.com. (
1414575123
10800
3600
604800
38400 )
ddns.example.com. IN NS ns1.digitalocean.com.
bob.ddns.example.com. IN A 8.8.8.8
When I ping bob.ddns.example.com on the server with bind installed I get 8.8.8.8, but when pinging for anywhere else I get the bind server IP.
Can I ask if what I am doing is possible ie, going from godaddy to tso, to another server and if so what NS records should I specify for bind? or is there something in the named config I need to change, I have set the following options in named.conf in an attempt to solve this issue.
listen-on port 53 { any; };
listen-on-v6 port 53 { any; };
allow-query { any; };
recursion yes;
I am aware that recursion may leave me open to DOS attacks and I intend to turn this to no eventually, but for the moment during testing I have left this to yes.
Any help or information would be greatly appreciated, I have been trying different variations of zone files etc without success, I am really though unsure as to if I am going in the right direction.
Hopefully I have made sense, but any further info I can provide, please let me know.
My first question would be - Are you sure you've updated the Registrar with this server as the DNS nameserver for this domain?
Use nslookup to find out:
# nslookup
> set querytype=NS
> server 4.2.2.1 (a DNS server on the Internet)
> ddns.example.com. (a closing dot helps avoid lookups using preferred search domains.)
and confirm that the Internet knows who to communicate with, and that your NS host is authoritative for the domain.
Next would be - Do you have any other nameservers up to "answer" for that subdomain, causing other problems?
BTW - glad to hear you fixed this issue!

Domain transfered to OVH but DNS Host is still on 1and1

I've transfered a domain from 1and1.com to OVH, now I need to manage my DNS to point them to a new server, but running this command from here
command line> nslookup
> set querytype=soa
> mydomain.com
I found out that DNS are still managed from 1and1.
Reading the OVH guide about DNS i found out that i need to activate DNS zone from my manager. But... won't this conflict with the DNS declared on 1and1?
I'm not sure about how is this working, so does someone knows the right workflow to do this?
Thanks in advance
after a call with OVH Support the correct workflow is:
Create or configure the DNS zone
Change the DNS Server to the OVH server
in 24 hours all should work fine, I'll let you know...

Plesk Nameserver Not Resolving

I have a VPS from myhosting.com with Plesk 11. I've set up dns in windows plenty of times but for the life of me I can't seem to get this working through Plesk. Here are my settings through Plesk and Godaddy... I asked myhosting about the setup and they said as far as they can see it seems correct but for the life of me the site will not resolve... Any help would be much appreciated!!
Plesk:
GoDaddy Host Names:
GoDaddy Nameserver Settings:
Enter your domain name here http://who.godaddy.com/ and in results:
Check "status" - should be ACTIVE
Check "Name Servers" it should be ns1.v...v.com, ns2.v...v.com
Check that ns1.v...v.com or ns2.v...v.com can be resolved by command:
nslookup ns1.v...v.com
I suppose that it will be NOT resolved because your NS servers are placed in zone which can be resolved yet.
The easiest way is to use some another DNS servers, maybe GoDaddy or some other DNS hoster.
Or you can make a trick:
change domain's DNS servers to GoDaddy DNS servers
In GoDaddy's domain management panel add in DNS zone records with: ns1.v...v.com, ns2.v...v.com
Wait until you can resolve ns1.v...v.com and ns2.v...v.com - it's about 24 hours.
Switch domain's DNS server back to ns1.v...v.com and ns2.v...v.com.
Wait until changes will be visible by other DNS servers like Google:
nslookup ns1.v...v.com 8.8.8.8
All should works now.

Resources