Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
Note: IP addresses and domain names have been changed to equivalents so as not to attract attacks!
Background
I'm setting up a standalone VPS on which I'll host half a dozen or so domains catering both email and web hosting. I may add additional VPSs later but don't want to register a new FQDN for each new server. I plan to have single domain name with a subdomain created for each server. For example s1.myserverdomain.com and s2.myserverdomain.com. These FQDNs will be used to provide resolvable names for common services like mail.s1.myserverdomain.com.
The first VPS will have two IP addresses, so that I can use it for providing nameserver services as ns1.s1.myserverdomain.com and ns2.s1.myserverdomain.com. Later, when I add another server, I'll split them up.
(You might tell me that this is bad practice to run both nameservers on the same machine, because in the event that one goes down, so will the other, but considering that in that instance, so too will the mail and web hosting, there doesn't seem much point paying for another server just yet.)
What I want to finish up with is with godaddy handling the DNS for myserverdomain.com and creation of nameservers for ns1.s1..., ns2.s1... on my VPS and later will transfer ns2.s1 to ns2.s2. I will set the nameservers for each of the half dozen hosted domains to use those nameservers.
My Configuration
So far I have created the following DNS records at Godaddy for myserverdomain.com in addition to the default records created automatically by Godaddy:
TYPE NAME VALUE
A s1 100.1.1.1
A ns1.s1 100.1.1.1
A ns2.s1 100.1.1.2
A mail.s1 100.1.1.1
A smtp.s1 100.1.1.1
There is a section on Godaddy for setting up hosts. I don't fully understand why this is, as I thought we just needed to create 'A' records to do that? Anyway, these are the hosts I've setup in that section:
HOST IP ADDRESS
s1 100.1.1.1
ns1.s1 100.1.1.1
ns2.s1 100.1.1.1
These records were all created more than 48 hours ago, so have completed propagation.
The VPS Setup
The VPS is running Ubuntu 18.04 with ISPConfig 3.1 installed for the panel. It was setup following "The Perfect Server" tutorial for ISPConfig which included the installation of Bind. The hostname was set to s1.myserverdomain.com from the outset.
The panel currently shows the status of BIND as being "UP".
Current Status
When I head over to mxtoolbox.com and perform a DNS check on s1.myserverdomain.com it reports "No DNS server can be found".
My Question
I need to know what I've done wrong. Are there any records I should have created? Of those I did create, are any unnecessary or wrong? Thanks!
Could be several things, maybe you have port 53 closed, maybe your NS records aren't set up correctly, etc...
You already noted how having the nameservers on the same machine is bad practice. Using a second IP is useless, I wouldn't bother. People can point a subdomains to a different IP address, and some DNS providers will wait a long time if they can't reach you, so even if your server is down for a minute, for some users it will be down for a long time.
If you share your domain name, we can look it up and see what's wrong. You can also do this yourself with tools like zonemaster.net and intodns.com
Lastly, ISPConfig has a good forum on howtoforge.com/community, I recommend it!
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
What are the main differences between BIND9 and Bundy? Is Bundy secure to use? I real on their website that:
The project is currently working on fixing up some loose ends in the
code inherited, clean the code, and to get the initial infrastructure
up and running to support the first Bundy release.
Is it buggy? Should I go with BIND9 or move to Bundy? I am running Debian Wheezy. If it is better than BIND9, how can I complete get rid of BIND9 and have no conflicts with Bundy?
Bundy is a rewrite of the BIND DNS system that is designed for a lot more scalability and security than BIND9. It is more complex to configure than BIND9 and includes much more modularity.
A BIND9 instance normally has the following service running:
Bind9/named
Bundy has the following services:
bundy-auth — Authoritative DNS server. This process serves DNS requests.
bundy-cfgmgr — Configuration manager. This process maintains all of the configuration for Bundy.
bundy-cmdctl — Command and control service. This process allows external control of the Bundy system.
bundy-ddns — Dynamic DNS update service. This process is used to handle incoming DNS update requests to allow granted clients to update zones for which Bundy is serving as a primary server.
bundy-msgq — Message bus daemon. This process coordinates communication between all of the other Bundy processes.
bundy-resolver — Recursive name server. This process handles incoming DNS queries and provides answers from its cache or by recursively doing remote lookups. (This is an experimental proof of concept.)
bundy-sockcreator — Socket creator daemon. This process creates sockets used by network-listening Bundy processes.
bundy-stats — Statistics collection daemon. This process collects and reports statistics data.
bundy-stats-httpd — HTTP server for statistics reporting. This process reports statistics data in XML format over HTTP.
bundy-xfrin — Incoming zone transfer service. This process is used to transfer a new copy of a zone into Bundy, when acting as a secondary server.
bundy-xfrout — Outgoing zone transfer service. This process is used to handle transfer requests to send a local zone to a remote secondary server.
bundy-zonemgr— Secondary zone manager. This process keeps track of timers and other necessary information for Bundy to act as a slave server.
Additionally, Bind9 still includes the DHCP server in it's installation. This feature is no longer in Bundy (it's the one piece that the ISC held onto)
https://ripe68.ripe.net/presentations/208-The_Decline_and_Fall_of_BIND_10.pdf
Starting in 2009, the Internet Software Consortium (ISC) developed a new software suite, initially called BIND10. With release version 1.2.0 the project was renamed Bundy to terminate ISC involvement in the project. [1]
I have a VPS hosted server with Windows Server 2003 on which I installed WAMP server, it is working and I am able to access it by localhost and modify it's contents with no problems. Also I have a domain name, say "domain-name.com". My question is how can I make it accessible on the internet by typing my owned domain name in browser?
This is quite an open question, but here goes:
You'll have to set a DNS record that points to your server. Your domain registrar may offer a DNS services themselves. If they do not, and only allow you to set nameservers, have a look at http://dns.he.net (a free DNS hosting service). In the latter case, don't forget to configure the nameservers in your domain registrars panel to the HE DNS servers (ns1.he.net - ns5.he.net)!
The records you will have to add are as follows:
An A record for www.domain-name.com, pointing to your IP
A CNAME record for domain-name.com (often represented in a DNS panel as #), pointing to www.domain-name.com
Optionally, MX and SPF/TXT records if you wish to use e-mail services on your domain/server (this is a whole separate subject to deal with, especially SPF records can be tricky)
Additionally, while this is not part of the question - please don't use WAMP for public/production servers. WAMP was made for development server setups, and it will be configured as such. If you really can't set up a HTTPd+PHP+MySQL setup yourself, then at least have a look at XAMPP, which is more suitable for live servers.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
Currently my network setup is as follows:
1 server, 3 ethernet cards.
eth0 - ISP1
eth1 - ISP2
eth2 - local network.
What would be the proper way of configuring primary and secondary DNS?
Using tinydns.
Current configuration:
2 tinydns services running on the same machine, each configured on a different ip (NS1 = eth0, NS2 = eth1)
each dns configuration contains both records:
NS1:
.domain.lv:10.10.10.10:ns.domain.lv
.domain.lv:20.20.20.20:ns2.domain.lv
#domain.lv:10.10.10.10:mail.didzis.lv:10:256::
#domain.lv:20.20.20.20:mail.domain.lv:20:256::
+www.domain.lv:10.10.10.10
NS2:
.domain.lv:20.20.20.20:ns.domain.lv
.domain.lv:10.10.10.10:ns2.domain.lv
#domain.lv:10.10.10.10:mail.didzis.lv:10:256::
#domain.lv:20.20.20.20:mail.domain.lv:20:256::
+www.domain.lv:20.20.20.20
The second link is more like a backup in case the first one fails and vice versa. Wont this configuration fail if eth1 is down and the www resolves to 20.20.20.20
Thanks!
This kind of configuration can work but there will be issues. What you want to do is make the TTL of the "www.domain.lv." record really low. The TTL tells other DNS servers how long they are allowed to cache the response. The lower you make it, the quicker clients will notice when one of your ISPs is down, but making it lower will also make it so they have to recheck the IP address more often, which will cost time. 300 seconds (5 minutes) might be a reasonable compromise but I would suggest making it longer (like 900 seconds) if you can afford for a failover to take 15 minutes.
By the way, I don't know how you set the TTL for a record in tinydns. I've never used it (and frankly I find its syntax quite cryptic and scary if your transcripts of the zonefiles are anything to go by).
This will all work fine when both ISPs are up.
The major drawback of this solution is that, when one of the ISPs is down, there will be DNS resolution delays no matter what. Lucky clients will try to query the nameserver that's still responding and get back the IP address that works for an answer. Unlucky clients will try to query the nameserver that's down first. This won't work. They will eventually fail over to the one that's still up and get a working IP address, but you must be prepared for a delay of (maybe) several seconds before this happens.
i have a linux client which uses pppoe to connect to the internet and
everytime this client comes online I wanna bind his ipadress to a subdomain.
dyndns is not an option due to their TTL.
It looks like i have to setup my own nameserver on my root server to accomplish this task because I cannot create the keys needed to run an nsupdate on the client with a provider nameserver... am I correct?
If so is there a good Howto for setting up a bind server for this specific task?
I havent ever maintained pppoe but if it uses dhcp to provide the ip address to the client, you could do updates from the dhcp to the dns.
Instructions on how to do this for debian here: http://www.debian-administration.org/article/Configuring_Dynamic_DNS__DHCP_on_Debian_Stable
Do not thou that you can adapt these to other distros too. You can find the same software atleast on fedora and ubuntu, difference is only how you install the required software.
One posibility is to set their machine to register with somebody like DynDNS. They have all the software you need to automatically notify them when they come online/go offline. This will give them a domain name of something like whatever.homelinux.org (it does not really matter). You then put static CNAME entries in your DNS to point your nice domain names eg southern.company.com to point to whatever.homelinux.org.
When they come online the domain will start to resolve and stop when they go off line since DynDNS have low TTL for this very reason. You can use large TTL in your zone file since the CNAMEs will not change.
Well dont you just need to create an A-Record for this IP on your DNS Server?
If your domain is 'google.com' and you wanted your host to be called 'server1'. Create an A-Record for 'server1' and point it to your machines IP.
Unless I am misunderstanding what you are asking for help with.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
We have setup 3 Virtual Machine server machines that mount the VMs from 2 other storage machines. We mount the VMs from the storage servers to have less data to move when moving the VMs(pause on one server, mount on new server, unpause) and to facilitate snapshots and backup.
We were in the middle of an extended power outage due to storms (the ops team forgot to check that we had fuel in the generator and the don't test it weekly tsk, tsk), so we shut everything down.
After fueling the generator, we started to bring everything up. Big problem.
To NFS mount the storage, NFS wants to do a reverse DNS lookup, but the DNS server is a VM that can't start until the storage is NFS mounted!
We copied the DNS server VM to one of the VM servers locally and started it so we could then bring everything up.
We would like to run NFS without the reverse lookup (everything is on our internal network) but can't find out how to turn off.
Any help is appreciated
Put the IP address of the NFS clients in the /etc/hosts file of the NFS server with a comment like:
# 2009-04-17 Workaround a chicken and egg DNS resolution problem at boot
192.0.2.1 mynfsclient
192.0.2.2 anothernfsclient
Then, add to your runbook "When changing the IP addresses of a machine, do not forget to update the hosts file of the NFS server".
Now, to shut off this stupid DNS test in the NFS server, it depends on the server. You apparently did not indicate the OS or the server type.
I had a similar problem with an old Yellow Machine NAS box - I was having DNS/DHCP fights where the reverse lookups were not matching the forward lookups.
In our case, just putting dummy entries in the NAS box /etc/hosts for all the IPs solved the problem. I don't even need to have correct names for the IPs - just any name for an IP solved stopped mountd from complaining.
(Interesting side note - at least in the older version of Linux on the NAS box, there's a typo in the NFS error message: "DNS forward lookup does't match with reverse " )
Can't you just put the ip address of the server in question in the fstab file and no dns lookup will be required.
It's NFS v4, the problem is that all the requests for access use a reverse DNS lookup to determine the NFS domain for access/security purposes.
I think you can stop this behavior by putting a line in /etc/default/nfs containing:
NFSMAPID_DOMAIN=jrandom.dns.domain.com
This needs to match across all the systems that are sharing/using NFS from each other. See the section about Setting NFSMAPID_DOMAIN, which is to the end of the page which explains what happens when it's not set.
NFSv4 - more fun than a bag of weasels.