Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have created two different views, view1 and view2 and copies of the same masterzone test.com for these two views. So when a client is asking for node1.test.com from ipaddrA (that matches view1), he gets answer but when another client is asking for the same node1.test.com from ipaddrB (that matches view2) he gets another response, lets say

This is correctly setup and works nice. But when I check in the db.test.com.view1 and db.test.com.view2 files, I see the A record entries as "glue records".

So the description in wikipedia, here What is a glue record? and in all the other sites that I have checked is not covering me because we are not having circular dependency.

Any help?

share|improve this question
When you say that you see them as glue records, what do you mean? What's marking them as glue records? –  Shane Madden Nov 25 '12 at 19:42
These records are not created in the db.test.com.view1 and db.test.com.view2 under resource records, but under glue records section. It says "glue records" and then these records are written. In contrast, if I create another A record in the default view, its written as a normal A record and not a glue record. So the dns server is marking them as glue records. –  edrimon Nov 27 '12 at 5:37
BIND just reads text files for zone data - it wouldn't have a glue records section (or any other sections). What interface are you looking at? –  Shane Madden Nov 27 '12 at 5:41
Of course BIND reads text files. And Ericsson's BIND server text file is having a glue records section. You are not helping me here.. I am pasting the interesting part from db.test.com.view1: ; Glue Records: 1.test.com. IN A ; Resource Records: <empty> –  maiky Nov 29 '12 at 16:26

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.