DNS ping doesn't reach our server for example:
ping clouddir1231.com
gives correct server IP in return but
ping abc.clouddir1231.com
gives same return without reaching our server as we have a docker service listening 0.0.0.0:53 for those subdomain resolution ping to log but nothing is received
I believe that you need to contact your provider about this issue. Please make sure you have pointed your domain to correct name server.
Related
I have an internal domain "smartxxxx.jo" in my company connected to the internet ...
and we have an external domain for email server and website with the same name.
on domain PCs the primary DNS address is the internal DNS Server IP "192.168.5.100" ... i cannot change it because sharing'll has issues !
when i want to access mail.smartxxxx.jo or smartxxxx.jo , it won't open and a message appears and say the website is not found, but when i try to access mail.smartxxxx.jo or smartxxxx.jo and the DNS server is disconnected ... it success ! ....
so , i think when I request smartxxxx.jo and the domain is connected to network , the local DNS is replay .... how to make DNS server direct the web address to the internet instead of searching locally
this issue appears even when i place www or the external website IP Address
The problem has been solved .... my issue wasn't because of split zone DNS >>>> the only thing i had to do was add a secondary dns server
http://gopalthorve.com/configure-secondary-dns-server-in-windows-server-2008/
I have a registered domain name, www.aaaDomain.com, assigned to ip address xx.xx.xx.xx . I set up my site on IIS8 to use the ip address xx.xx.xx.xx and port 8020 for my website. I can connect to the website when I type xx.xx.xx.xx:8020 in a browser but I cannot connect to the website when I use www.aaaDomain.com:8020
Also, I have another website on this same server as my Default website. When I type just the domain name without the port number, my default website comes up (because DNS does not allow adding port numbers) just like when I type in the ip address without the port number.
What am I doing wrong?
Here is what my site binding looks like on IIS8.
As you already have an existing site running on the server you should check your security settings on both the Windows firewall and any other security/firewall settings you have - It sounds like you have not opened the additional port which you have just configured in IIS.
Check to see if you can ping the new site by its domain name - that will verify that you have the correct DNS setup, you can also try & browse to it via the server console (or remote desktop) if that works then its security setting somewhere blocking your access. Even if the ping request times out it should still resolve the name to an IP address for you to check. You may find that ICMP is also blocked.
If you just changed your dns record, be aware that you should wait up to 72 hours for the dns to replicate after changing your dns record.
I have a domain,
www.xyz.co.uk
now I would like to point for example,
www.data.xyz.co.uk to the ip address of my server(digitalocean)
So far what I did is, I have created a hostname on dns managementconsole of godaddy, with data.xyz.co.uk and pointed that to my ip address.
I am little confused wether that is it or I need to do more on my server ? Secondly when I do ping data.xzy.co.uk in terminal I get unknown host response.
Could somebody points me in right direction.
I manage to get the resolved the issue by adding A record in DNS settings of my hosts account and pointing that record to a desired Ip.
I am having issues with my DNS. I am setting up a new domain and have Windows Server 2008 R2. The domain controller is running on Hyper-V. Of course I can ping the FQDN internally on the Domain controller but not the host server.
When pinging the Netbios name from host the DNS resolves and ping is successful. When pinging using using FQDN (server1.contoso.local) I receive Ping request could not find host server1.contoso.local. Please check the name and try again.
I have done nothing to the network besides setting up the Active Directory. IP6 is disabled. The server and DC have static IPs and my router is the DHCP provider. The DC is DNS.
setup is as follows:
IP: 192.168.0.199
Subnet: 255.255.255.0
Default gateway: 192.168.0.1 (router internal IP)
Preferred DNS: 192.168.0.100 (DC IP)
Alternate: 192.168.0.1
When I attempt to join the domain I have to use the Netbios name (FQDN will not work; could not contact active directory domain controller). I am prompted to enter domain password but then receive the following error: "The following error occurred attempting to join the domain "domain-name" An attempt to resolve the dns name of a domain controller in the domain being joined has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target domain."
I have disabled the firewal on both the host server and the DC. I have attempted a /flushdns and a /registerdns. No changes. When attempting to renew the ipconfig on the DC I receive the following error: "An error occurred while releasing interface Loopback Pseudo-Interface 1: the system cannot find the file specified"
Is my problem simply a missing DNS entry? I unfortunately do not know much about DNS.
Thank you in advance.
I was able to resolve this issue on my end by adding the domain name suffix to the host's NIC.
I actually just resolved my issue. One key bit of information I completely forgot to mention was that I have 2 NICs installed and in use on my server. One of them is assigned strictly to the VM Domain Controller. Because of this a virtual network connection was created. For some reason that I don't entirely understand this was affecting my ability to see the FQDN on my network. I corrected the DNS settings on the virtual NIC and all my NETBIOS woes have left.
I don't really understand why that caused the problem, but changing the virtual NIC DNS server settings which defaulted to my router instead of my DC fixed the problem.
I am trying to set up my own nameserver on hp cloud VPS for the domain "appwared.com".
I added ns1.appwared.com from my registrar control panel to point to my server's public ip address.
I installed NSD3 as my DNS software and configured the zone files. It is up and running but as you may see, the domain is not resolving.
here you can see the zone file: http://pastebin.com/z0094kja
This is my first attempt to set up my own Name Server, maybe you can peoint out what I am doing wrong.
Thanks!
HP was blocking the UDP 53 port that used in DNS.