Tag Info

Hot answers tagged

6

After you have added ipa_dyndns_iface = eth0 in that pastebin i see sssd recognize your ip as multicast: "(Tue Jul 9 10:00:01 2013) [sssd[be[example.us]]] [ok_for_dns] (0x0200): Multicast IPv4 address 172.25.50.227" in the piece of code Jacob wrote where he would test for looback addresses, multicast addresses e.t.c. not to report to dns you will find ...


5

Yes, some sort of dynamic DNS setup would work best. There are plenty of free dynamic DNS services, or you can run your own with a bit of BIND and nsclient.


5

Because it actually isn't an instant change with DynamicDNS or CloudFlare. No matter what service you use, there is a time starting at the time you make the change lasting until the cached records expire on all the other DNS servers in the world. This time is governed by the TTL, which for some services (like DynamicDNS) is kept low to allow for frequent ...


4

Amazon's solution is called an "Elastic IP address" - a static external IP address that always points to your machine, regardless of its internal address. There's some information on it on the ec2 page, and more information on how to configure it in this walkthrough (which is aimed at solving a slightly different problem, but still mostly applicable here)


4

So far it has happened (to you) just once and that was for extraordinary reasons. Considering the drawback of dynamic DNS I really don't think it's worth the bother. If you still want to do it anyway just get one of the DDNS clients and run it on the server itself, as that's the only place it will work correctly. If you are seriously concerned you should ...


4

Actually Bind is capable of doing dynamic dns updates through RFC 2136 standard messages. Using the nsupdate tool and the right configuration (not terribly hard but not completely trivial either). Your options for authenticating these update messages are 1) allowing only certain IPs to send update messages 2a) TSIG symmetrical encryption 2b) SIG(0) based ...


4

I just went through this process, and want to note some issues that tripped me up. First, this is the canonical reference for configuring ddns for namecheap: http://www.namecheap.com/support/knowledgebase/article.aspx/583/11/how-to-configure-ddclient If you don't want to rely on an external web service for finding your IP (like me), things are slightly ...


3

My suggestion would be to move your name servers to DynDNS, set up your DNS records there, and install one of their dynamic DNS clients somewhere on your local network to keep your dynamic ip address in sync with your DNS records. I use DynDNS and host 6 web sites at home using their dynamic DNS client.


3

You've already mentioned DynDNS, it sounds like all you're missing is the client. They mention a couple linux-compatible clients on their website. ddclient inadyn Using either of these in combination with a dynamic DNS service should accomplish what you want. I originally assumed that your shared hosting would provide you with shell access. Without ...


3

Where do you host the name servers for example.com? I assume with the the company that hosts www.example.com. Here is what you do: Set up your dyndns client so that it updates myhomeserver.dyndns.org with your dynamic IP where myhomeserver.dyndns.org is the domain name you selected from dyndns. Configure your DNS through your hosting company's DNS control ...


3

Yes, you can edit a registry key on the servers themselves to tell them not to register ptr records, you can find it here: SYSTEM\CurrentControlSet\Services\Tcpip\Parameters The registry key is DisableReverseAddressRegistrations Set it to 1 to not register PTR records, 0 to turn it back on. Usual Registry editing warnings apply


3

It sounds like you need to port forward TCP port 3389 to the server in the router/firewall.


3

Use check_client_access. Insert it before reject_rbl_client: smtpd_client_restrictions = permit_mynetworks, permit_sasl_authenticated, check_client_access hash:/etc/postfix/rbl_override, reject_rbl_client zen.spamhaus.org, permit Add in /etc/postfix/rbl_override your.dynamic.dns OK Don't forget to run postmap ...


3

After setting up scavenging on a DNS zone in Windows, you need to reload the zone in order for the proper "this zone can be scavenged after" date to be calculated and set. Reloading the zone should fix your issue.


3

We did not have much luck with this. In your described scenario our clients did not reliably fail over using the method you describe. I recommend a load balancer between the two servers so that requests are directed to a VIP and can be handled by whichever server is available.


3

I would expect it to be the name of the host e.g. myhost as the zone would be dyndns.org.


3

You'll likely pay $0.50 or $0.51 a month. DNS queries are cached, so a user should really only be making a billable DNS query every once in a while. For dynamic DNS a TTL of 10 minutes is probably a good idea, for other stuff an hour or a day is common.


3

By default the client itself does its own DDNS update if it is XP or newer. A DHCP server can perform proxy updates for DNS clients that don't support updating their own client records. You can also force a client registration via ipconfig /registerdns Here's a good link, simple enough: http://technet.microsoft.com/en-us/library/cc771255.aspx Domain ...


3

You could do this with delegation. It's easier if all the remote records are under a single sub-domain, like let's say you have cloud.domain.com and your BIND server has a zone matching that. In Windows DNS, create a sub-domain (right click the zone, click New Domain...), call it cloud. That looks like a sub-folder. Within there, create NS records that ...


2

The registration process begins with a start-of-authority (SOA) query for the zone in question, so your clients should be able to dynamically register just fine if their configured DNS servers are not primaries for the zone. If your clients get their addresses from DHCP, then the default is that the clients will register the A records and your DHCP server ...


2

No, it isn't technically required to have a separate zone for dynamic updates. I think the biggest factor in using sub-domains for dynamic DNS has to do with security policies for updating the zone. In my opinion the permissions you can set in bind aren't very flexible, though newer versions are somewhat better. With allow-update (Bind 8.*) permissions ...


2

The absolutely easiest solution is to use one of the free dynamic DNS services like dyndns.com or no-ip.com (Google for more options). If you need to have your home pc on your "mydomain.com", I suggest using a CNAME pointing to the dyndns fqdn.


2

Looks like this is not doable. I tried to lab it, and the secondary DHCP fails with errors in the syslog about not being allowed to update the zone.


2

When I used DynDNS for their free dynamic service, I used foobar.dyndns.net as the domain and had the wildcard redirect enabled. That let everything work more or less transparently, since I could have local DNS and use vhosts to make sites appear at the same URLs on the inside and the outside. crb is completely correct that you can use whatever you want as ...


2

There need be no connection between any external DNS name and any hostnames/internal DNS. What you call the hostname (sometimes the 'local part'), should be alphanumeric, no dots. There's a whole RFC on how to pick a name. Your DNS suffix ('domain name') is added to hostnames when you try and resolve them. As you say, even if you have servers 'foo' and ...


2

is nsupdate what you're looking for. It can be used to make dynamic changes to suitably configured BIND installations. nsupdate -k /etc/somekeyfile > server 127.0.0.1 /* address from the controls section of named.conf */ > zone local > update add usvr.local 86400 cname ubuntuSVR.local > send /* add the record */ > update delete usvr.local ...


2

Since your servers are all private I'm assuming your not wanting to publish the IP addresses to the greater internet. This actually simplifies things. I know for my small networks I've had success with dnsmasq, a dead simple DNS and DHCP server. It should allow clients to add themselves to the DNS server when they get a DHCP lease. Further reading: ...


2

I did setup bind with dynamic updates via nsupdate (as CarbonLifeForm described), and combined this with a simple Perl-Script which gets called via encrypted HTTPS REST-Request, checks subdomain/password combination and then calls nsupdate with the IP of the request. Example Update-Call from any client (which will automatically set the appropriate subdomain ...


2

Presumably you've had to set up a windows domain for exchange to work properly, is this server the domain controller too? If so it will automatically register itself as the top-level domain A record. Also, yes there is a way you can work around this. Open network connections, right click on the NIC in question, click tcp/ip v4 then click properties. In the ...



Only top voted, non community-wiki answers of a minimum length are eligible