Realityloop | Drupal solutions tailored to your needs

Realityloop | Drupal solutions tailored to your needs: "Ægir to be a major time saver and great tool for deplying Drupal websites, so several months ago we started on the path to get Aegir running locally on our Mac's for development purposes, with one caveat.. using NGINX instead of Apache!

Without further ado here is how to do it both by Video and Text instructions, please follow the instructions carefully as this process has been refined to make the process as painless as possible. "

'via Blog this'

What is "reverse DNS" and do I need it? [KB1052]

What is "reverse DNS" and do I need it? [KB1052]: "ard DNS in who points the zone (domain name) to your DNS server.
With forward DNS, you point the zone to your DNS server by registering that domain name with a registrar.
With reverse DNS, your Internet connection provider (ISP) must point (or "sub-delegate") the zone ("....in-addr.arpa") to your DNS server.
Without this sub-delegation from your ISP, your reverse zone will not work.

Reverse DNS is mostly used by humans for such things as tracking where a web-site visitor came from, or where an e-mail message originated etc.
It is typically not as critical in as forward DNS - visitors will still reach your web-site just fine without any reverse DNS for your web-server IP or the visitor's IP."

'via Blog this'

How do I get reverse DNS for my IP addresses delegated to my own DNS server? [KB1187]

How do I get reverse DNS for my IP addresses delegated to my own DNS server? [KB1187]: "Reverse DNS is controlled by whoever "owns" the IP address.
The owner can choose to sub-delegate reverse DNS for a range of IP range to someone else, who in turn can sub-delegate parts of that range further, etc.

IANA ultimately "owns" all Internet IP addresses.
IANA delegates these IP addresses to 5 regional registires; AfriNIC (Africa), APNIC (Asia/Pacific), ARIN (North America), LACNIC (Latin America), and RIPE (Europe, Middle East, Central Asia).
And these registries delegate their IP addresses to backbones providers and ISPs, who delegate to end-users.

So as an end-user, if you want control of reverse DNS for your IP addresses, you need to contact whoever provides you with these IP addresses, and ask them to do a reverse DNS sub-delegation to your DNS servers."

'via Blog this'

How to sub-delegate a reverse zone [KB1240]

How to sub-delegate a reverse zone [KB1240]: "ARIN (which is *usually* a Class B), then you should do your own DNS sub-delegation for any block you reassign that is larger than class B. Everything smaller than that you should use the CNAME method.
I think your distinction comes from the fact that it used to be that (mostly) ARIN assigned Class B's to ISPs who then reassigned to their customers. However, I have worked in multiple locations where we had direct assignments from ARIN that were smaller (/20 to /23). In those cases, when we reassigned parts of our block and wanted to also delegate the reverse DNS to them, we simply added NS records. The number of DNS redirects is kept to a minimum and ARIN doesn't have to get involved in your business.
"

'via Blog this'

How to sub-delegate a reverse zone [KB1240]

How to sub-delegate a reverse zone [KB1240]: "Sub-delegate from less than a class C (< 256 IP addresses)

If you have an IP address range of less than 256 IP addresses, then the best way to sub-delegate reverse DNS for part of that range is to ask your IP address provider to create/change this delegation on their DNS servers.
Technically you could create another level of CNAME redirection similar to "classless IN-ADDR.ARPA delegation" (see above) but this is not recommend because the redirection becomes too deep."

'via Blog this'

How to sub-delegate a reverse zone [KB1240]

How to sub-delegate a reverse zone [KB1240]: "NS: 64/30.33.22.11.in-addr.arpa -> ns1.customer.com
NS: 64/30.33.22.11.in-addr.arpa -> ns2.customer.com
CNAME: 64.33.22.11.in-addr.arpa -> 64.64/30.33.22.11.in-addr.arpa
CNAME: 65.33.22.11.in-addr.arpa -> 65.64/30.33.22.11.in-addr.arpa
CNAME: 66.33.22.11.in-addr.arpa -> 66.64/30.33.22.11.in-addr.arpa
CNAME: 67.33.22.11.in-addr.arpa -> 67.64/30.33.22.11.in-addr.arpa

Your customer would setup a zone called "64/30.33.22.11.in-addr.arpa" on his DNS server with the following records:

SOA: 64/30.33.22.11.in-addr.arpa ...
NS: 64/30.33.22.11.in-addr.arpa -> ns1.customer.com
NS: 64/30.33.22.11.in-addr.arpa -> ns2.customer.com
PTR: 64.64/30.33.22.11.in-addr.arpa -> [reverse DNS name for IP 11.22.33.64]
PTR: 65.64/30.33.22.11.in-addr.arpa -> [reverse DNS name for IP 11.22.33.65]
PTR: 66.64/30.33.22.11.in-addr.arpa -> [reverse DNS name for IP 11.22.33.66]
PTR: 67.64/30.33.22.11.in-addr.arpa -> [reverse DNS name for IP 11.22.33.67]"

'via Blog this'

http://buildasite.us

"$ORIGIN 2.0.192.in-addr.arpa.
@ IN SOA my-ns.my.domain. hostmaster.my.domain. (...)
; ...
1 CNAME 1.A.domain.
2 CNAME 2.A.domain.
; ...
129 CNAME 129.B.domain.
130 CNAME 130.B.domain.
;"

'via Blog this'