Sei Satzparad's questions

Let's say I have a couple of separate Linux NSD servers. How can I make the master server share changes with the slave servers?

NSD appears to have this functionality. It can declare zones as master or slave. I'm pretty sure I understand how to set up the communication in the config files.

What are the commands necessary after a zone update on the master server to propagate the changes to the slaves? Is it entirely automatic once NSD's cache is updated, or is some intervention necessary?

Edit: Solved, please remove.

My problem is this.

Dissatisfied with the existing free DNS nameserver solutions, I decided to make my own nameservers for my websites. I'm using NSD on Debian, and it's working great. I can request a record from the server with DIG and get the correct response and all that jazz.

However, there's a catch that I can't figure out how to circumvent. In order to give my nameservers to my domain registrar, they need A records. (ns1.example.com etc.)

Here's the issue: Since I'm having these servers handle the DNS for all of my domains, I'm not sure how to create A records for the servers themselves. If I create the ns1, ns2 records inside my own server, my registrar won't be able to look them up. But in order to create those records externally so I can point a registrar to my servers, I need to register those A records with an external source, right?

How can I bootstrap the A records for my nameservers so my registrar can see them long enough to plug in? Or am I misunderstanding the problem entirely?

I hope that made a bit of sense.

So here's the problem.

"Someguy" wants to transfer his domain and website to me so I can take care of it. But Someguy's primary email address is "[email protected]". If he transfers thatsite.com's DNS to me, the emails will no longer get to his provider.

I could just set the MX records for thatsite.com to point back to his email provider so he would keep getting his email, but then I couldn't have an email at thatsite.com.

What I need to do is configure Postfix so it sends only emails addressed to [email protected] back to his provider's mail servers.

root@omega-15:/var/unreal/src# find ./ircd
./ircd
root@omega-15:/var/unreal/src# ./ircd
bash: ./ircd: No such file or directory

What the hell is this? Bash thinks that the file doesn't exist, when it obviously does.

-rwxr-xr-x 1 unreal unreal 2075069 Jul 20 04:01 ircd
ircd: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, not stripped

All I want to do is install postfix, and forward emails. I don't need anything to stay on my server. This is giving me hell. I tried the best I could, but postfix is denying all relays.

What I want is this. Say my server is at example.com. I want this:

Email forwarding:

[email protected] -> [email protected]
[email protected] -> [email protected]
[email protected] -> [email protected]

All I need is a forwarding box that redirects emails coming to it. Since there's obviously something wrong with my configuration, I could really just use an example main.cf for my purpose, and I'll be on my way.

Edit: Logs

The strange thing is the logs don't give me any errors.

main.cf:

mreiley@Omega-14:/var/log$ cat /etc/postfix/main.cf
# See /usr/share/postfix/main.cf.dist for a commented, more complete version


# Debian specific:  Specifying a file name will cause the first
# line of that file to be used as the name.  The Debian default
# is /etc/mailname.
#myorigin = /etc/mailname

smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu)
biff = no

# appending .domain is the MUA's job.
append_dot_mydomain = no

# Uncomment the next line to generate "delayed mail" warnings
#delay_warning_time = 4h

readme_directory = no

# TLS parameters
smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
smtpd_use_tls=yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache

# See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for
# information on enabling SSL in the smtp client.

myhostname = omega-14.omegadev.org
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
myorigin = /etc/mailname
mydestination = omega-14.omegadev.org, localhost.omegadev.org, localhost
relayhost = 
mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = all

virtual_alias_domains = omegadev.org monovec.com ifmovement.org
virtual_alias_maps = hash:/etc/postfix/virtual

mreiley@Omega-14:/var/log$ 

virtual forwards file:

mreiley@Omega-14:/var/log$ cat /etc/postfix/virtual
[EXPUNGED]@omegadev.org [email protected]
[email protected] [email protected]

mreiley@Omega-14:/var/log$ 

Then I send an email from gmail to test the configuration. This is what mail.log shows:

Jul 16 16:00:32 Omega-14 postfix/smtpd[4282]: connect from mail-px0-f179.google.com[209.85.212.179]
Jul 16 16:00:32 Omega-14 postfix/smtpd[4282]: 72784483A: client=mail-px0-f179.google.com[209.85.212.179]
Jul 16 16:00:32 Omega-14 postfix/cleanup[4287]: 72784483A: message-id=<[email protected]>
Jul 16 16:00:32 Omega-14 postfix/qmgr[4274]: 72784483A: from=<[email protected]>, size=2026, nrcpt=1 (queue active)
Jul 16 16:00:33 Omega-14 postfix/smtp[4288]: 72784483A: to=<[email protected]>, orig_to=<[email protected]>, relay=gmail-smtp-in.l.google.com[74.125.53.27]:25, delay=1.5, delays=0.08/0.01/0.08/1.3, dsn=2.0.0, status=sent (250 2.0.0 OK 1279321231 d5si4147919wam.28)
Jul 16 16:00:33 Omega-14 postfix/qmgr[4274]: 72784483A: removed

The log claims that the delivery was a complete success, but the email never shows up in my inbox or spam folder.

However, if I use telnet, I get a different story.

mreiley@Omega-14:/var/log$ telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 omega-14.omegadev.org ESMTP Postfix (Ubuntu)
helo omegadev.org
250 omega-14.omegadev.org
mail from:[email protected]
250 2.1.0 Ok
rcpt to:[email protected]
554 5.7.1 <[email protected]>: Relay access denied

Update! It would seem that GOOGLE ITSELF is blocking me. Emails sent to other providers go through, but when sent to gmail they don't even hit spam.