We published a site which works on IIS, but recently we encounted a issue, it is very slow if user access site through domainname but fast with IP.
We finally solved it by change the web server DNS address.
What I don't know is what is the root cause? Why the server dns makes this issue?
Related
I have a Bluehost VPS account and I need to point my external domain which is purchased from porkbun to my VPS server. After some research, I have changed the A record in the domain registrar to my VPS server IP and changed name servers to Bluehost servers(which are ns1.bluehost.com and ns2.bluehost.com). Currently, when accessing the domain I'm seeing the default Bluehost page, but it does not seem to be connected with the server as it does not display any file I'm updating in the root folder. Is there any step I'm missing? I have tried changing nameservers of the VPS server itself by editing DNS settings in the domain, but any of them does not seem to be working. Any help on this would be highly appreciated.
If you are trying to 'browse' to your VPS server then you would need to add an 'A' record type into the DNS for the domain name.
For example, if you are browsing to 'test.mydomain.com' and your VPS IP Address is '192.186.1.15' then you should add an A Record into the domain zone file with the following detals:
Host Record - test
Points To - 192.168.1.15
These details are taken from the following page:
https://www.bluehost.com/help/article/dns-management-add-edit-or-delete-dns-entries#add
So recently I setup a webserver on windows 10 at my place (Frontend Angular 2). I setup all the necessary stuff like DNS, Hostfile, Firewall... Then I bought a domain and added my global ip to that domain. Everything worked fine until today, where my place had a power failure.
So I restarded the server and the router and noticed that I have a new global IP. So I changed the IP at the frontend and the backend and updated the IP at my domain name provider.
Now my problem is, that the domain isn't connecting to my webserver anymore - its timing out. But when I enter my global IP everything is working fine.
Any advices what I might have forgotten?
It turns out, that from the network where I'm accessing the domain it must have been some kind of domain caching. Because the domain is accessible for people that are not on the same network as I am. So it actually works, just not for me in my particular network.
I registered domain on the WHM and create a new user cpanel with the domain, the domain is added to the cpanel. But when i try to browse the domain name it getting server DNS address could not be found.i updated the name servers with my server name, but nothing changed.
when i try to go through myip/~newuser it going fine to the site file, but with the domain name it's not.
You have a DNS issue in this case. Please check your DNS zone with a tool like intoDns:
https://intodns.com/yourdomain.tld
See if you get any errors there. If you do, then you have issues with your DNS configuration. Be sure that you have create the parent DNS servers for your domain if you want to use the DNS from WHM (the parent DNS servers should point to your WHM server ip).
Try using external services to query your DNS server to see if it actually works (like MXToolBox etc). Or you can use nslookup or dig right from your WHM server by connecting via ssh.
The company i work for just begun hosting a new website and had to transfer the domain name from the ISP to a different hosting company.
Now the website is accessible from outside the network but not accessible from inside the network. The ISP is the same and we can't access the website using our ISP. It doesn't resolve the DNS Name at all.
If i try to ping the website, it says "host lookup failed", even nslookup is failing. When trying to access the website via the IPaddress, it refuses.
The problem is in the ISP but I don't know how to solve it and our ISP isn't being very helpful.
This often happens when someone is running authoritative and recursive DNS on the same servers. Which is why you should never do that :)
It also happens when your local domain (Active Directory?) is the same as the domain you use at your hoster. Never do that. For example: if your domain is example.com then don't use example.com as your local domain. If you do then both your hoster and your own servers believe they are authoritative for that domain. Once the zone data starts to diverge you have this kind of weird problems. Instead use a subdomain of your domain name for your office, like office.example.com so that example.com can remain authoritative at the hoster.
If you do have the same domain both locally and at the hoster then you have to manually make sure that the information in your local DNS server stays in sync with the hoster's DNS server. For example: if your hoster has record www.example.com A 192.0.2.1 then you have to have the same record in your local DNS server. When the hoster changes the record to e.g. www.example.com A 192.0.2.222 then you have to make the same change otherwise your local DNS server will keep telling you that www.example.com is at 192.0.2.1. The same happens when you change hoster as they will almost certainly use different IP addresses.
So if you can then don't use the domain name itself in your office but use a subdomain. If that is impossible then you will have to manually keep the hoster's and your own DNS zone data in sync. Because this always goes wrong and breaks in 'interesting' ways really try to use a subdomain though!
PS: and never ever use somebody else's domain name as your local domain. I have seen ICT companies use local domains like <localcityname>.com and then suddenly the whole company can't access the real domain anymore because the local servers think it's theirs.
Okay, can't seem to find a great article or info on this. My client purchased a domain for his company (domain.com) through Network Solutions. He has a local server running Windows 2008 R2 that he wants to host his company's website on. I've created the website and have it running with Apache on localhost. The server does have a static IP, but when I visit it, I'm prompted for credentials (user, password) which is expected as it's meant to be protected.
My question:
How would I point the domain to the website on his server?
From what I've researched, I have options that include:
Pointing the domain to the static IP (what about the credentials?)
Creating A and CNAME records for the DNS server on Network Solutions
Setting up a local DNS server w/ Active Directory on the Windows machine
Creating a couple name servers that would tell Network Solutions
where to send the domain
It's safe to say I'm effectively confused, so any help would be very much appreciated.
So basically you have to associate the domain name to the IP address, and that is done using DNS.
I'd suggest option 2 where you let Network Solutions manage the DNS, and you create an A record for www.domainname.com that points to the IP address on your server. Keep in mind it might take 24-48 hours for this new record to propagate across the internet. Take a look at http://www.networksolutions.com/support/dns-manager-advanced-tools/ and http://www.networksolutions.com/support/a-records-ip-addresses/
Regarding the credentials prompt, I assume you are using IIS and so you'd want to check the Authentication settings for the site. If you want anonymous access to the site, you would enable it there.